Managing search queries of a search service

ABSTRACT

The invention relates to a method for managing search queries of a search service. A first search query is received from a client application and executed by a search service. A content item of a search query type of a search index of the search service is provided as a first search result of the first search query. A search query with a user-defined search specification provided by the first search result is automatically executed as a second search query and one or more content items of the search index are provided as a second search result of the second search query by the search service. The second search result is sent as a search result of the received first search query to the client application.

BACKGROUND

The present disclosure relates to the field of electronic data processing and, more specifically, to managing search queries of a search service.

Client applications, also referred to as search-based applications, may rely on a search service to identify and retrieve information that is required for the functionality of the client application, like content and navigation elements. The client application sends during runtime search queries to the search service and retrieves the information that is required, e.g., for rendering application views from search results of the search queries. The application views present content items retrieved from the search service to a user of the client application.

SUMMARY

Various embodiments provide a method for managing search queries of a search service as well as a computer program product and a computer system for executing the method as described by the subject matter of the independent claims. Advantageous embodiments are described in the dependent claims. Embodiments of the present invention can be freely combined with each other if they are not mutually exclusive.

In one aspect, the invention relates to a method for managing search queries of a search service. The search service comprises a search index with a set of content items and a search engine. The set of content items comprises a set of one or more content items of a search query type. Each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword.

The method comprises receiving a first search query from a client application. The first search query compromises at least one boosting factor referring to at least one of the keywords of at least one of the content items of the search query type. The received first search query is executed by the search service. In response to the executing of the first search query, a content item of the search query type comprising the at least one keyword referred to by the boosting factor is provided as a first search result of the first search query by the search service. A search query with a user-defined search specification provided by the first search result is automatically executed as a second search query by the search service. in response to the executing of the second query, one or more content items are provided as a second search result of the second search query by the search service. The second search result is sent as a search result of the received first search query to the client application.

In a further aspect, the invention relates to a computer program product comprising a non-volatile computer-readable storage medium having computer-readable program code embodied therewith for managing search queries of a search service. The search service comprises a search index with a set of content items and a search engine. The set of content items comprises a set of one or more content items of a search query type. Each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword.

The managing of the search queries comprises receiving a first search query from a client application. The first search query compromises at least one boosting factor referring to at least one of the keywords of at least one of the content items of the search query type. The received first search query is executed by the search service. In response to the executing of the first search query, a content item of the search query type comprising the at least one keyword referred to by the boosting factor is provided as a first search result of the first search query by the search service. A search query with a user-defined search specification provided by the first search result is automatically executed as a second search query by the search service. in response to the executing of the second query, one or more content items are provided as a second search result of the second search query by the search service. The second search result is sent as a search result of the received first search query to the client application.

In a further aspect, the invention relates to a computer system for managing search queries of a search service. The search service comprises a search index with a set of content items and a search engine. The set of content items comprises a set of one or more content items of a search query type. Each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword.

The computer system comprises a processor and a memory storing machine-executable program instructions. Executing the program instructions by the processor causes the processor to control the computer system to receive a first search query from a client application. The first search query compromises at least one boosting factor referring to at least one of the keywords of at least one of the content items of the search query type. The received first search query is executed by the search service. In response to the executing of the first search query, a content item of the search query type comprising the at least one keyword referred to by the boosting factor is provided as a first search result of the first search query by the search service. A search query with a user-defined search specification provided by the first search result is automatically executed as a second search query by the search service. in response to the executing of the second query, one or more content items are provided as a second search result of the second search query by the search service. The second search result is sent as a search result of the received first search query to the client application.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the following, embodiments of the invention are explained in greater detail, by way of example only, making reference to the drawings in which:

FIG. 1 depicts a schematic diagram illustrating an exemplary cloud computing node according to an embodiment,

FIG. 2 depicts a schematic diagram illustrating an exemplary cloud computing environment according to an embodiment,

FIG. 3 depicts schematic diagram illustrating exemplary abstraction model layers according to an embodiment,

FIG. 4 depicts a schematic diagram illustrating an exemplary system for managing search queries of a search service according to an embodiment,

FIG. 5 depicts a schematic diagram illustrating an exemplary system for managing search queries of a search service according to an embodiment,

FIG. 6 depicts a schematic flow diagram of an exemplary method for creating content items of a search query type according to an embodiment,

FIG. 7 depicts a schematic flow diagram of an exemplary method for managing search queries of a search service according to an embodiment, and

FIG. 8 depicts a schematic flow diagram of an exemplary method for implementing user-defined search query specifications according to an embodiment.

DETAILED DESCRIPTION

The descriptions of the various embodiments of the present invention are being presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Embodiments may have the beneficial effect of allowing a user to personalize a client application in form of a search-based application. The personalization may be enabled by implementing user-defined search query specifications used by the search service to retrieve data in form of content items for use by the client application. The personalization may comprise adapting the user experience and/or the behavior of the application. The user may be enabled to personalize an appearance of a user interface used by the search-based application to display data content retrieved from a search service using a search query with user-defined specifications. The personalization may, e.g., comprise a personalization, i.e., user specific amendment of a content of a menu, a sequence of menu items, an appearance and/or a sequence of navigation elements etc. This personalization may be implemented by adapting, i.e., personalizing, search queries that are used by the search service for determining elements of the user interface of the search query, i.e., for determining elements comprised by an application view displayed by the user interface. The personalized search queries may be second search queries which are determined by the search service as search results of first search queries received from the client application. The first search queries may be non-personalized search queries. These non-personalized search queries may be used to determine personalized second search queries. The results of the respective personalized second search queries are sent to the client application by the search service as search results of the received first search queries.

For example, a search-based application may implement a web shop comprising a product catalog. Following the search-based application programming model described herein, the client application issues search queries to retrieve the data for menu items and for navigation paths for navigating through the respective web shop, for selecting and inspecting products or services offered via the web shop as well as for ordering and/or downloading/using the respective products or services. However, e.g., a menu provided by the web shop may not fully satisfy an individual user, e.g., lacking a menu item and/or a navigation path to a favorite product or service of the user or a sequence of the menu items may not be ordered according to preferences of the respective user. Thus, the user may want to improve the set of menu items and/or their sequence as provided by a user interface of the client application in form of an application view.

Embodiments may allow the user to adapt the search-based application himself/herself. More precisely application views provided by the search-based application on a user interface may be adapted by the user without being required to wait for a developer to update the application code. To do so, the user may use a user interface control component which enables the user to initiate a modifications of content items managed by a content management system providing the search service. The modified content items represent second search queries for retrieving, e.g., the menu items. Using the user interface control component, the user may create a personalized version of a second search query to implement an enhanced, i.e., personalized, ranking, e.g., for improving the sequence of menu items. According to embodiments, the modifications may get effective as soon as the user saves the same. The modifications may get effective for all installations of the client application on all clients for the respective user, without requiring an update of the client application.

Embodiments may further have the beneficial effect of enhancing the user experience of a search-based application and thus improving user confidence and user productivity as well as lowering maintenance and support costs.

According to embodiments, the search service and a search query management component are provided by a content management system. The query management component is configured for managing the receiving of the first search query from the client application and the sending of the second search result to the client application. Embodiments may have the beneficial effect that second search query with user-defined search specifications may be managed by the content management system using the query management component as content items of the search query type.

According to embodiments, the content item of the search query type comprising the at least one keyword referred to by the boosting factor is provided in response to the executing the first search query to the search query management component as part of a set of ranked content items of the search query type. The search query type comprising the at least one keyword referred to by the boosting factor is the top ranked content item comprised by the set of ranked content items and selected by the search query management component for providing the second search query. A boosting factor may be provided in form of a numerical factor assigned to a keyword and defining a relative boosting of search results comprising the respective keywords over search results not comprising the respective keyword.

Embodiments may have the beneficial effect that the boosting factor is used for ensuring that second search queries comprising a keyword referred to by the boosting factor are preferred over second search queries comprising no such keywords. The keywords may be selected to identify second search queries comprising user-defined search query specifications, e.g., a user identifier identifying a user of the client application providing the user-defined search query specification or a user group identifier identifying a user group comprising the respective user.

Embodiments may have the beneficial effect of exploiting one of the following features of a search engine: The search engine may provide a ranking feature which allows to create a ranking of a set of content items determined as search results according to flexible criteria. For example, a correlation between a user identifier that is part of the search queries executed by the search engine and the determined content items. If there are personalized versions of a content item of the search query type, i.e., versions of a content item comprising a specific user identifier and/or a specific user group identifier, the search query management (SQM) component and/or the client application are safe to pick the content item top-ranked based on the respective identifier and do not need to implement custom logic to assess the relevance of multiple returned content items.

A ranking feature of the search engine may automatically rank the personalized versions of content items of search query type, e.g., content items comprising a user identifier and/or a user group identifier, higher than non-personalized versions of content items of search query type.

According to embodiments, the ranking of the content items of the search query type is higher the more keywords referred to by the at least one boosting factor of the first search query the respective content item of the search query type comprises. Embodiments may have the beneficial effect that a top ranked second search query is a search query with the most keywords referred to by the boosting factor, i.e., search query personalized for a given user as far as possible. For example, second search queries may comprise one keyword referred to by the at least one boosting factor at most. For example, second search queries may comprise more than one keyword referred to by the at least one boosting factor. According to embodiments, the ranking of the second search query may be influenced and/or defined by boosting factor assigned to a keyword comprised by the respective second search query.

According to embodiments, the first search query comprises as set of disjunctively connected sub-queries. According to embodiments, one of the disjunctively connected sub-queries comprises as a boost query the boosting factor. Embodiments may have the beneficial effect that the respective disjunctively connected sub-queries may be used as a boost factor to ensure that second search results comprising more extracted keywords are ranked higher than second search results comprising fewer extracted keywords. A disjunctive connection implements a logical “or” as a truth-functional operator of a set of operands which is true if and only if one or more of its operands are true. For example, the extracted keywords are added using the following sub-query structure: “OR <keyword_field>:keyword1 OR <keyword_field>:keyword2 OR <keyword_field>:keyword3 . . . ”. According to embodiments, the respective keywords may be assigned with numerical boosting factors.

According to embodiments, one of the disjunctively connected sub-queries comprises a search query identifier identifying the second search query. Embodiments may have the beneficial effect of ensuring that second search queries referred to by the first search query using the search query identifier identifying the second search query are preferentially taken into account as a potential first search result.

According to embodiments, the boosting factor is assigned to a user identifier identifying a user of the client application. According to embodiments, wherein the boosting factor is assigned to a user group identifier identifying user group comprising the user of the client application. Embodiments may have the beneficial effect of ensuring that a potential personalized version of the second search query comprising assigned to a specific user or a user group identifier comprising the specific user is ranked higher than a non-personalized version without a user related identifier. Embodiments may have the beneficial effect that a scope of a modification may, e.g., by the user, be restricted to a single user or be valid for an entire user group comprising the respective user.

According to embodiments, the method further comprises creating the content items of the search query type. The creating comprises determining one or more search queries comprised by a code of the client application. A content item of the search query type is created for each of the determined search queries. The content item of the search query type comprises a second search query with the search query specification of the respective determined search query and a search query identifier identifying the respective second search query. The created content items of the search query type are stored in the search index of the search service. The determined search queries are updated for use as first search queries by the client application.

Embodiments may have the beneficial effect of providing a method for creating the content items of the search query type starting with a client application and a search service not configured for using second search queries in form of content items of the search query type yet.

According to embodiments, an initial setup may be performed in order to enable a given search-based application to take advantage of user-defined search queries. The setup may comprise scanning an application code and properties files of the given search-based application and creating a set of content items of the search query type. The setup may be executed automatically by a setup component provided by the content management system. The creating of the content items of the search query type may be executed automatically and comprise invoking an authoring API of the authoring service. Furthermore, the code of the search-based application may be modified. The modifying may comprise a replacing of the search service as a target of search queries issued by the client application with an SQM component as a replacement target. The SQM component may be comprised by a content management system which comprises the search service as well. The SQM component may reflect a search service API and act like a search service proxy. After the initial set up, first search queries issued by the client application may be sent to the SQM component which forwards the same to the search service. Furthermore, the search service may be enabled to retrieve in response to executing a first search query a content item of the search query type providing a second search query. If a second search query is provided by content item of the search query type as a first search result, the search service may automatically execute the second search query and provide a second search result of the second search to the client application as a result of the first search query issued by the application.

According to embodiments, the search query identifier identifying the respective second search query is a unique identifier. Embodiments may have the beneficial effect that second search queries may be unambiguously identifiable. Nevertheless, different versions of the same second search query comprising different user-defined modifications of the search specifications may comprise the same unique identifier. These may be distinguishable based on different keywords, e.g., user identifiers and/or user group identifiers.

According to embodiments, the updating comprises storing the updated search queries in the search application and replacing invocations of the determined search queries comprised by a code of the client application by invocations of the updated search query. Embodiments may have the beneficial effect of ensuring that the updated search queries referring to the content items of the search query type are used by the client application for retrieving data using the search service.

According to embodiments, the content management system further provides an authoring service which enables creating and editing content items. The authoring service is used by the search query management component for the creating of the content items of the search query type.

According to embodiments, an overview content item comprising an overview over the determined search queries updated and the content items of the search query type created is provided in the search index. The method further comprises updating the overview content item for each of the determined search queries updated and each of the content items of the search query type created. Embodiments may have the beneficial effect of providing an overview for the user of the client application about the progress of a setup of content items of the search query type for the client application.

According to embodiments, the method further comprises implementing the query management component as a target for search queries received from the client application. Embodiments may have the beneficial effect that first search queries are received by the query management component which is thus enabled to effectively and efficiently manage the search queries executed by the search service.

According to embodiments, the method further comprises receiving by the search query management component a first search query from the client application comprising a modification intention identifier identifying an intention for a user-defined modification. The received first search query with the modification intention identifier is forwarded by the search query management component to the search service for executing. In response to the forwarding, a set of one or more ranked content items of the search query type is received by the search query management component from the search service. A top ranked content item of the search query type is selected from the set of ranked content items of the search query type by the search query management component. In response to a detecting of the modification intention identifier of the received first search query by the search query management component, the selected top ranked content item of the search query type is sent as a search result of the received first search query with the modification intention identifier to the client application for displaying on a user interface.

Embodiments may have the beneficial effect of providing second search queries to the user. The user is thus enabled to implement user-defined search specifications. The client application may provide a user interface (UI) control component enabling the user to individually modify and thus personalize the search-based application user experience and behavior. The UI control component may allow to modify a search query that is used to retrieve elements for rendering an application view. The UI control component may provide guidance for the user regarding how to modifying the query, e.g., by showing a graphical representation, by offering a preview, by checking the modification and/or by recommending certain modifications.

According to embodiments, the search query management component is further configured for implementing user-defined search queries. The implementing of a user-defined search query comprises receiving by the search query management component a user-defined version of a content item of the search query type in the search index from the client application. The user-defined version comprises a search query specification of the respective content item of the search query type in the search index with one or more user-defined modifications, a search query identifier identifying the respective search query of the respective content item of the search query type and depending on a user-defined scope for the modification the user identifier identifying the user of the client application or a user group identifier a user group comprising the user client application of the as a keyword. The user-defined version of the content item of the search query type is stored in the search index.

Embodiments may have the beneficial effect of implementing user-defined search queries, i.e., personalized versions of the content items of the search query type comprising user-defined search specifications.

The above described mechanism ensures that the SQM component, when providing elements for rendering an application view of the client application, retrieves and uses the personalized second search query provided by the content item. Thus, the SQM component may return personalized search results in response to first search queries issued by the search-based application, which enable the search-based application to render a personalized view of the client application.

According to embodiments, the content management system further uses the authoring service for the implementing of user-defined search queries.

According to further embodiments, the SQM component may be implemented as part of the client application. The SQM component may interact with the search service and the authoring service provided by the content management system through the API gateway.

A basic search-based application pattern based on second search queries provided as content items of a search query type may comprise a two-phase search process. By issuing one or more first search queries to the search service, the search-based application may retrieve content items, comprising content data, menu items, navigation elements, like links to other pages or views, to be presented to the user in an application view. The menu items and navigation elements are represented as content items in the search index, and may be managed i.e. created, read, updated and/or deleted (CRUD), through an authoring service. The search service executes the first search queries and returns the resulting content items to the search-based application. The resulting content items may be ordered according to a ranking computed by the search service or a sub-component of the search service.

According to the two-phase search process, the search results returned to the search-based application are not the first results retrieved by the search service executing the first search queries. The process rather uses second search queries provided as content items of the search query type. These second search queries are not managed by the client application. For example, the second search queries provided by the content items of the search query type are managed by a content management system. Thus, a personalized search of the search service may be implemented by personalizing the second search queries without a requirement to modify the client application.

In order to be able to provide personalized second search queries, the first search queries issued by the client application may comprise, e.g., an application identifier identifying the client application as well as an application view identifier of a certain application view of the client application as additional search parameters. Alternatively, a second search query identifier identifying a second search query may be added as an additional search parameter. Thus, the first search queries may search for specific second search queries or second search queries assigned to the respective application and/or application view. Theses second search queries may be personalized. Personalization may comprise modifying the search parameters of the respective second search query according to user individual preferences and/or assigning the second search query to the user or a user group comprising the user by adding a user identifier identifying the user or a user group identifier identifying the user group, respectively. The first search query may as part of a boost sub-query comprise the user identifier and/or the group identifier, thus ensuring that a potential personalized version of the second search query comprising the user identifier or user group identifier is higher ranked than a non-personalized version without the respective identifiers. The first query and its execution implement the first phase.

The second phase is implemented by the second search query and its execution enabling a personalized search. The search index of the search service comprises a set of content items representing second search queries. These content items are referred to as content items of the search type and may comprise a representation of a search query in a suitable syntax, e.g., in Solr query syntax, as well as a set of keywords used for finding an/or ranking the content item. These keywords may comprise a client application identifier identifying a client application and/or a second search query identifier identifying a second search query as well as optionally a user identifier identifying a user and/or a user group identifier identifying a user group. In case the second search query is personalized for multiple users or groups of users, there may be multiple personalized versions of one second search query for different users or user groups. The second search query may be created or modified either automatically, e.g., by a tool or an automatic adaptation method, or by a content author directly editing the corresponding content item of the search query type in the authoring service. The search service may find, rank and return a set of one or more second search queries in response to executing a first search query received from the client application.

A content management system managing the content items including the content items of the search query type may either automatically execute a top-ranked second search query and return the resulting second search result in reply to the first search query to the client application or may return a set of one or more ranked second search queries to the client application, which may execute the top-ranked second search query using the search service. The client application uses the second search results of the second search query received in reply to the first search query to render an application view. The client application may rely on the ranking of the second search results for selecting or sequencing content items, like menu items, navigation elements, etc. in the application view.

Modifying the second search query to take into account user-defined search query specifications may directly influences the user experience of the application without requiring a code change in the client application. An application view rendered using the second search result of the modified second search query may be defined by the user according to user individual preferences. Thus, the user experience of a search-based application may be enhanced. An intuitive and easy to use method for extending and personalizing a search-based application may be provided. Furthermore, user confidence and user productivity may be improved as well as maintenance and support costs be lowered. After the setup of the content items of the search query type, this method may be implemented to work automatically without requiring modifications and/or code changes in the client application.

In a service-oriented software architecture, a service refers to a software component which provides an application programming interface (API) configured to be accessible or invokable by other services or software components using a standard protocol or a standard invocation mechanism. A service may be implemented, created, removed, deployed, started and stopped independently of other services.

An API refers to a set of predefined methods of communication among software components. An API may comprise a set of subroutine definitions, communication protocols, and/or tools for building software. Thus, an API may provide a set of building blocks which may be combined for developing computer programs. An API specification defining an API may, e.g., comprise specifications for routines, data structures, object classes, variables, an/or remote calls.

In a service infrastructure, multiple instances of one service may be running in order to improve fault tolerance, throughput and load balancing of service requests. Each of the instances of the service may provide the same APIs and the same functionality. Each of the instances may be based on the same implementation, e.g., code, docker image and/or deployment artifact.

An interaction of a first service with a second service may comprise sending a service request for invoking an operation of one of the APIs provided by the second service. A service request may comprise an identifier of the requested API operation, e.g., in form of an URL or another parameter. In addition, a service request may comprise further data relevant for processing the service request.

A service infrastructure may comprise at least one service registry providing functionality for a service discovery and/or service lookup. A service registry may manage information about active, i.e., running, services of the service infrastructure. Before a first service invokes a second service, the first service may send a lookup request to the service registry containing a set of one or more criteria for selecting the second service, such as a service name and/or service identifier. A service name may be hardcoded in an implementation of the first service. Upon receipt of the lookup request, the service registry may select a service instance which adheres to the specified one or more criteria specified by the lookup request and return information about the selected service instance to the first service. The respective information may comprise an address, e.g., an URL, hostname, IP address and/or port, for use by the first service to create and send an invocation request to the second service. In case there is no service satisfying the one or more criteria specified by the lookup request, the service registry may return an error message.

A service registry may maintain information about a status and/or health of each service instance and consider only healthy services for service discovery requests, i.e., service lookup requests. In case a service instance becomes unresponsive and/or unhealthy, the service registry may no longer provide an address and/or information about the respective service instance to other services. The service registry may further incorporate a load balancing algorithm for distributing load between service instances, e.g., using random choice, round robin, and/or least connections.

A service may register at the service registry, e.g., immediately after starting. The registering may for example comprise sending a registration request including an address of the service to be registered. The registration request may further comprise data like, e.g., a service identifier and/or a set of identifiers of one or more APIs provided by the service to be registered. The service registry may, e.g., regularly, invoke a health check, e.g., in form of a status request, on each registered service. The invoked service may respond by returning status information. The status information may, e.g., comprise a flag indicating whether the respective service is healthy or unhealthy. If the returned status indicates a problem or if a service does not respond in time, the service registry may flag the respective service as unhealthy.

According to embodiments, a service registry may select a service instance based on two simple criteria: a binary flag representing a health status of the respective service and a service identifier, like, e.g., a service name.

A services infrastructure may be built using cloud computing. A computing component of the cloud may be separated from the Internet, e.g., by a firewall. An API gateway may provide access to client applications, i.e., client application programs, like mobile applications executed on a mobile communication device, e.g., a smartphone, to desktop applications executed on desktop computers, scripts executed in a browser, etc. An API gateway may receive requests issued by client applications and create a service lookup requests using the client requests. The service lookup requests may be sent to the service registry by the API gateway. In response to sending the service lookup requests, the API gateway may receive one or more addresses of service instances to be invoked and send invocation requests to the respective service instances. In response to sending the invocation requests, the API gateway may receive responses from the respective service instances and create one or more responses to the client request using the responses received from the service instances. The responses created by the API gateway may be returned to the requesting client applications.

While processing a request received from an API gateway, a service instance may need to invoke another service. For this purpose, the service instance may prepare a lookup request, send the prepared lookup request to a service registry, receive in response to sending the lookup request an address of a service instance and invoke the respective service instance using the received address.

Services may use state of the art software engineering mechanisms, like, e.g., caching, persistent storage, session and state management, connection and thread pooling, etc. For example, caching may improve performance. A computer system may cache, i.e., store in a cache memory, data that was recently used, e.g., while processing recent requests. Since requests may be distributed between service instances, individual service instances may have different cache entries. In other words, the state of a service instance may depend on an individual usage history of the respective service instance. Service performance may depend on whether data relevant for processing a request is available in a cache memory assigned to the respective service or not. Thus, service performance for processing the same request may differ between individual service instances. It is therefore preferable to intelligently select service instances for processing a request.

A service performance may depend on the data in a cache memory assigned to the respective service. However, there may be no standard for sharing detailed information about cache contents between service instances and service registries. Thus, this information may not be available during service lookup, e.g., for selecting a particular service instance.

A service infrastructure and a service implemented therein, like, e.g., a search service, may serve multiple users and multiple tenants. A tenant refers to a group of users, e.g., a company, who share a common access with specific privileges to a software instance, i.e., a service instance. The service infrastructure and implemented service may ensure that tenant specific data assigned to a particular tenant is isolated from other tenants. Client requests and service requests may comprise a tenant identification identifying a tenant which is associated with the respective requests. The tenant identification may enable the service infrastructure component to establish a context and state required for processing the respective requests.

A content management system (CMS) may manage a creation of digital content items, such as text documents, webpages, images, videos, code scripts, etc. A content management system may support multiple users in a collaborative environment. Modern enterprise-scale content management systems may be based on separate content authoring and content delivery systems. Thereby, different requirements of content creation and retrieval tasks may be met. A process responsible for creating, modifying and editing content may take place in the authoring system and be referred to as authoring. A process responsible for transferring content from the authoring system to the delivery system may be referred to as publishing. A content is either transferred as it is, e.g., text, video, images, static files, or in a transformed formed, e.g., in pre-render templates.

A content management system may provide an authoring user interface for editing and managing content items. A content management system may be configured as a headless CMS, i.e., may not provide a visual user interface, but rather provide a set of APIs, which may be called by client applications to create, edit and retrieve content items.

This may allow a client application to provide a user interface and functionality for content authoring as well as to invoke APIs to create, edit and retrieve content items.

An authoring system may allow content authors to create, edit and manage content items. The authoring system may include an authoring user interface or may just provide authoring APIs. Furthermore, the authoring system may allow to upload or import files.

A content management system may further provide a publishing system configured for publishing content items from the authoring system to a delivery system or component, like a content delivery network (CDN), to make the content available to the public. The publishing system may also incorporate further functionalities, like indexing content items in a search index, modifying, transforming or pre-rendering content items, etc. Publishing may be started manually by a content author, may be invoked on schedule or may be invoked via a publishing API operation.

A content management system may provide a functionality to define different types of content items. For example, the content management system may provide a predefined list of possible content item types. The type of a content item may, e.g., be selected by the user using an authoring system or component. The content management system may represent and store the content item type as a specific field in the content item. The respective field may, e.g., be named “type” or “classification”. For example, a content management system may provide the following predefined content item types: “content”, “asset”, “page”, “page template”. A content management system and client applications, which retrieve and use the content items, may handle content items of different type separately. For example, a client application may use a first content item of type “page” to render a view of a page.

A content management system may be deployed in a cloud environment and implemented as a set of interacting services. An API gateway may provide an API to application programs, like, e.g., client application, authoring application, etc. and forward requests and responses between the respective applications and the services provided by the content management system.

A content management system may comprise a search service component or may alternatively use a search service external to the content management system. An authoring system may allow content authors to search for content items, a publishing system may index published content items in a delivery search index, thereby allowing client applications to search for content items. The authoring system may index content items in an authoring index, when a content item is created, updated or deleted. The publishing system may index content items during publishing. As part of publishing, the publishing system may further update a configuration of the search index and invoke a learning to rank method in a training mode in order to recalculate a ranking model.

End users may rely on a search service to find a certain content in the website, like, e.g., products in a web shop. Furthermore, content management system client applications may use the search to lookup content to be rendered and content for establishing, e.g., a page hierarchy for navigation. Therefore, search quality and relevance ranking of search results may be important for end users as well as for an operator of a website.

A search service may provide functionality for searching in unstructured data, like, e.g., text documents. For this purpose, a search service provides functionality to create a search index by indexing content items, i.e., data to be searched, like, e.g., text documents. A search index may contain a representation of a data content to be searched, in a representation which is suited, e.g., improved, for processing by the search service. The search service may provide an application programming interface API for indexing content items, which makes the respective content items searchable by the search service. Furthermore, the search service may provide a query API allowing a client, e.g., another service or an application, to issue a search query. A search query may contain a set of query parameters specifying search criteria for searching content items, like, e.g., a set of search terms. The search service may process the query by selecting and ranking a set of content items according to a search query. The ranking may determine a scoring or an order of the respective content items relative to the search query, which represents for each of the content items a level of relevance in relation to the respective search query. A search query may also contain parameters for controlling the ranking, like, e.g., a ranking query, a boost query and/or a boost function. Furthermore or alternatively, a search service may automatically select one or more heuristics and/or parameters for a search ranking. A search ranking may for example be based on statistics about the search index and the search terms used for a search. Furthermore, the search ranking may be based on statistics of an occurrence of search terms in specific content items.

For a ranking, e.g., the tf-idf method (term frequency-inverse document frequency) may be used, which is a numerical statistic intended to reflect an importance or relevance of a word for a document in a search index. Tf-idf values may be used in a search service as weighting factors in ranking a document's relevancy relative to a given search query. An tf-idf value increases proportionally to the number of times a word appears in a document and is offset by the frequency of appearance of the word in the search index.

A search service may manage multiple search indexes, e.g., assigned to multiple tenants. Thus, a search service may be used in a multi-tenant environment, e.g., by creating a separate search index for each tenant. In this case, search client services may be required to select the correct search index to use for search requests depending on a tenant context.

A search index may be associated with a specific search configuration, consisting of multiple configuration parameters defining settings which control search functionality, behavior and, e.g., the structure of the content items in a search index. Search configuration parameters may be updatable and/or changeable via a search service API or by uploading a set of configuration parameter changes, e.g., in form of one or more configuration files, to the search service, a file system or a persistent storage the search service is using.

A headless content management system may be used to support a programming model for client applications, herein referred to as search-based applications or search-based application programs. Search-based applications rely on a search service to identify and retrieve contents, navigation information, site structures and/or page structures, etc. that are required for the functionality of the respective application. For example, during runtime a client application may send a series of search queries to a search service and retrieve information required for rendering the current view of the application from the search query responses. In contrast to other programming models, the application may, e.g., not use databases, file systems or other persistency components for managing this information. In order to support the search-based application, the content management system may provide the search service for the search-based application.

Content authors may use the content management system to edit information that is relevant for the search-based applications, like site structures, page structures, navigation structures, and contents, as well as assets, like images, videos, etc. Using this information, content authors may further create new pages, author new content, define new content types and/or define new page types. A modified site may be reviewed, approved, and subsequently published using the content management system. A CMS publishing component used for publishing may index the data in a search service. Therefore, when the publishing is completed, the data may be available to search-based applications through interfaces of the search service.

A search-based application may rely on sending search queries to a search service to retrieve content and the navigation elements to be presented to a user. User interface components may be used for rendering information, like, e.g., page headers and page footers for rendering a page, site maps, trees, menus, or links for rendering the site structure or navigation structure, etc. This way, layout aspects may be separated from the content, site structure and navigation structure.

Embodiments may have the beneficial effect that search queries used by a search-based application are not hardcoded in the application code as defined by an application developer during development of the respective search-based application or provided in a properties file which is part of the respective application. Instead the search queries to retrieve data used by the search-based application, such as content items, are managed in the content management system. For this purpose, a second search query may be represented as a content item or a set of content items of a specific content type, i.e., the search query type. This allows a content author to use the normal authoring functionality to create and edit second search queries, which are handled like content items by the content management system.

The search queries of the search-based application are changeable without modifying the application. In order to be able to use modified search queries a user is not required to update or redeploy a modified version of the application comprising the modified search queries on a client device.

Embodiments may have the beneficial effect that by modifying the second search queries, i.e., the search results of the first search queries, the functionality of the search-based application may be influenced without requiring a code change in the search-based application.

According to embodiments, the computer program product further comprises computer-readable program code configured to implement any of the embodiments of the method for managing search queries of a search service described herein.

According to embodiments, the computer system further is configured to execute any of the embodiments of the method for managing search queries of a search service described herein.

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computing node is shown. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, such as e.g., PCI, PCI-X and PCIe.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 2) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 3 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes, in one example IBM® zSeries® systems; RISC (Reduced Instruction Set Computer) architecture based servers, in one example IBM pSeries® systems; IBM xSeries® systems; IBM BladeCenter® systems; storage devices; networks and networking components. Examples of software components include network application server software, in one example IBM Web Sphere® application server software; and database software, in one example IBM DB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter, WebSphere, and DB2 are trademarks of International Business Machines Corporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. For example, cloud storage locations, e.g., a virtual storage of virtualization layer 62, may be provided. Metering and Pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. For example, the identity of a user trying to access storage locations provided by the cloud infrastructure may be verified. User portal provides access to the cloud computing environment for consumers and system administrators, e.g., access to storage locations provided by the cloud infrastructure. Service level management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; transaction processing; a search service, wherein means are provided for managing search queries executed by the search service. The search service is, e.g., provided by a content management system configured for managing search queries of a search service.

FIG. 4 depicts a schematic diagram illustrating an exemplary system for managing search queries of a search service 106. The system may comprise a computer system, e.g., a cloud computing node 10, which provides a content management system 100. The content management system 100 manages digital content items, in particular a creation and modification of digital content items. Digital content items may, e.g., comprise text documents, webpages, images, videos, code scripts, etc. The content management system 100 comprises an authoring component 102 providing an authoring service for creating, modifying and editing content items managed by the content management system 100 as well as a persistent storage 104 for storing the content items created, modified and/or edited by the authoring component 102.

The content management system 100 further comprises a search service 106. The search service 106 may provide a search engine, i.e., an information retrieval software program configured for information retrieval and presentation in response to search queries. The search engine is configured for searching one or more search indexes 108, 110 with content items managed by the content management system 100. The search indexes 108, 110 contain representations of data content to be searched. The representation may be configuring to improve processing of search queries. The content items comprised by the search indexes 108, 110 may, e.g., comprise content items of the search type providing second search queries. The search indexes 108, 110 may be tenant specific search indexes 108, 110, i.e., assigned to specific tenants. Depending on which tenant requests a search, the search service 106 may select one of the search indexes 108, 110 assigned to the requesting tenant. The search is then executed by the search engine according to the request using the selected search index 108, 110.

The search service 106 further search query management (SQM) component 112. The SQM component 112 has an interface to the authoring service 102 and an interface to the search service 106. The authoring service 102 as well as the search service 106 may be provided by the content management system 100. The content management system 100 may manage content items of a search query type. Such content items of the search query type comprise second search queries which are provided as results of first search queries. In other words, the content items of the search query type represent second search queries used for retrieving data for search-based applications 118, 120. The content items of the search query type may comprise a search query specification and a set of one or more keywords. The search query specification may be provided in any search query syntax suitable for defining search queries to be executed by the search service 106. The content management system 100 may handle, store and publish the respective content items of the search query type like content items of any other content type. During publishing, the content management system 100 may index the content items in the search service 106. The indexing may enable client applications 118, 120 to search for a content item of the search query type, i.e., a second search query, by issuing a first search query to the search service 106 comprising a set of one or more keywords.

The content management system 100 and more precisely the search service 106 may receive search queries, i.e., first search queries from the client application 118 via an API gateway 116. A client application 118, 120 in form of a search-based application may rely on the search service 106 of the content management service 100 to identify and retrieve content items, e.g., comprising content data, navigation information, site structures and/or page structures, etc. that are required for the functionality of the client applications 118, 120. For example, the client applications 118, 120 may send during runtime a series of search queries via the API gateway 116 to the search service 106. The search service 106 executes the search queries using one of the search indexes 108, 110 assigned to the user of the client applications 118, 120. Thus, the client applications 118, 120 are enabled to retrieve information required for rendering an application views from the search results received. Thus, the client applications 118, 120 may not require databases, file systems or other persistency components for managing on their own.

The client applications 118, 120 each comprise a user interface (UI) control component 117, 119 for enabling the user to personalize search queries, i.e., generate user-defined search query specifications for use by the content management system and the search service 106. The UI control components 117, 119 may allow to modify search queries that are used to retrieve elements for rendering application views. The UI control components 117, 119 may provide guidance for the user regarding how to modifying the query, e.g., by showing a graphical representation, by offering a preview, by checking the modification and/or by recommending certain modifications. After modification of a second search query according to user preferences with a UI control component 117, 119, the user may store the modification. The storing may comprise sending the modified second search query via API gateway 116 to the search query management component 112 for implementing the modified second search query in one of the search indexes 108, 110.

FIG. 5 depicts a schematic diagram illustrating an alternative system for managing search queries of a search service 106. In FIG. 5, SQM components 112, 121 are implemented as part of the client applications 118, 120. The SQM components 112, 121 interact with the search service 106 and the authoring service 102 provided by the content management system 100 via the API gateway 116.

FIG. 6 depicts a schematic flow diagram of an exemplary method for creating content items of a search query type. The creation of content items of a search query type may, e.g., be executed as part of an initial setup of the client applications and the content management system. The method may comprise for each search query found in the application code of the search-based application: In block 200, a unique search query identifier is created for the respective search query identify the same. In block 202, a content item of the search query type is created assigned to the respective search query. The content item of the search query type comprises the search query specification of the respective search query and the unique search query identifier. The search query specification may, e.g., be extracted from the application code. For creating the content item of the search query type the authoring API may be used. The resulting content item of the search query type provides a second search query assigned to the first search query. The second search query, which may be provided as a first search result of the first search query, may provide the beneficial effect of being personalizable without requiring a personalization of the respective first search query. In block 204, the search query found in the application code is updated. According to embodiments, the updating may comprise modifying the search query in the application code or providing an additional search query in order to replace the search query in the application code. The updated search query may be provided to the client application for use as a first search query for retrieving data from the search service using. The updated search query may comprise one or more, e.g., disjunctively connected, sub-queries. At least one sub-query may comprise the unique identifier identifying the respective search query in the application code and thus the updated search query. The unique search query identifier may be used to determine a content item of the search query type assigned to the respective first search query as a first search result providing a second search query. Furthermore, at least one sub-query may comprise a boost query in form of a sub-query comprising a user identifier identifying the user of the search-base application and/or one or more user group identifiers of user groups the user of the search-base application belongs to. By taking into account user identifiers and/or user group identifiers only those content items of the search query type assigned to the respective user and/or a user group comprising the respective user may be determined as a first search result of the respective first search query. Thus, the second search queries may be personalized by assigning the respective content items of the search query type individual users and/or a user group comprising the respective user. Optionally, the one or more sub-queries may comprise one or more keywords. The keywords may, e.g., be extracted from the application code. According to embodiments, the updated search query is a copy of the respective search query in the code supplemented by one or more of the aforementioned sub-queries.

In block 206, the application code may be modified to invoke an SQM component provided by the content management system instead of the directly invoking the query search service, when the search-based application issues a first search query. In block 208, as an optional step a content item of an overview type may be created and/or updated. The content item of the overview type may comprise a human readable overview over the set of processed search queries in the application code and the created content items of the search query type. The blocks 200 to 208 may be executed as a loop for each search query found in the application code until no further search query are found and the initial setup is finished. Embodiments may have the beneficial effect of rebuilding and/or updating a search-based application and providing the rebuilt and/or updated application for redeployment. After the initial setup, a content author as well as any user of the search-based application may be enabled to personalize the search-based application by reviewing first search queries and editing second search queries directly in the authoring service. The content author and/or user are enabled to edit and modify the second search queries without requiring an update of the search-based application. Blocks 200 to 208 may be repeated in loop for each search query found in the application code of the search-based application and ended, when all search query found have been handled. According to embodiments blocks 200 to 208 are executed automatically by a setup tool. According to an alternative embodiment, blocks 200 to 208 may be executed manually by an application developer.

FIG. 7 depicts a schematic flow diagram of an exemplary method for managing search queries of a search service. In block 300, the client application issues a first search query including a search query identifier identifying the respective first search query as well as a sub-query which boosts to at least one keyword. The respective keyword may, e.g., be a user identifier of a user of the client application and/or a set of one or more group identifiers identifying user groups to which the respective user belongs to. The user identifier and/or user group identifiers may be used to identify personalized second search queries. In block 302, the SQM component receives the first search query issued by the search-based application. In block 304, the SQM component forwards the received first search query to the search service. In block 306, the SQM component receives an ordered set of one or more content items of the search query type as a first response to the first search query. The ordered set may, e.g., be received in form of a ranked list. The ordered set comprises at least one content item providing a second search query including the first search query identifier. The list may, e.g., be ranked based on the boosted keywords identified by the boost sub-query. If the set comprises multiple first search results for the first search query, content items comprising a boosted keyword, e.g., the user identifier, may be ranked higher. The ranking may be implemented taking into account the number of boosted keywords comprised by each first search result and/or weight factors, i.e. boosting factors, assigned to the respective boosted keywords. The more boosted keywords a first search result comprises and/or the higher the comprised boosted keywords are weighted, i.e., the larger the weight factors, the higher the first search result is ranked. In block 308, the SQM component selects one or more top ranked first search results. For example, the SQM component may select the top ranked first search result or a set of one or more top ranked first search results exceeding a predefined threshold. The threshold may define a number of one or more boosted keywords which first search results are required to comprise in order to be selected and/or a number which the accumulated weight factors of the boosted keywords have to exceed. In block 310, the SQM component retrieves one or more personalized second search queries from the selected one or more first search results and automatically executes the respective second search queries by invoking the search service. In block 312, the SQM component receives one or more second search results of the one or more executed second queries. In block 314, the SQM component sends the received one or more second search results as search results for the first search query to the client application. According to embodiments, the second search results may be received as an ordered set of one or more second search results, e.g., in form of a ranked list, and the top ranked second search results or a set of one or more second search results exceeding a predefined threshold may be selected for sending in block 314.

FIG. 8 depicts a schematic flow diagram of an exemplary method for implementing user-defined search query specifications. In block 400, a first search query to be modified, i.e., to be personalized, is determined. In block 402, the determined first search query is issued and sent to the SQM component of the content management system, adding a specific query parameter indicating that the respective first search query is determined for implementing a modification. In block 404, the first search query is forwarded by the SQM component to the search service and processed by the search service. While processing the search query, the SQM component may recognize the known specific query parameter and—in contrast to the normal mode of operation—return the top ranked second search query as a search result to the UI control, including an identifier identifying the respective second search query as well as keywords. In block 406, the UI control component receives and displays the respective second search query. The UI control component may allow the user to edit the received second search query, e.g., either by directly modifying the search query specification comprised by the respective second search query or by interactively modifying a graphical representation of the respective second search query. In block 408, a scope of the modification is selected using the UI control component. The scope of modification may either restrict the modification to a personalization for the respective user only or may define the modification to be valid as a personalization for a full group of users comprising the respective user. In block 410, a set of one or more keywords is selected depending on the selected scope using the UI control component and used to modify the second search query. The modifying may comprise adding the selected keywords to the second search query, e.g., in order to boost the second search query as a first search result for the first search query. The set of keywords may either comprise a user identifier identifying the respective user or one or more group identifier identifying one or more user groups comprising the respective user. In block 412, when the user chooses to store the modified second search query, the UI control component may be used to send the modified second search query to the SQM component. The modified second search query, may comprise the modified search query specification, the identifier identifying the respective second search query and the scope dependent keywords selected using the UI control component, i.e., either the user identifier or a user group identifier. In block 414, the SQM component receives the modified second search query and creates an additional content item of the search query type representing the search query. This additional content item is created to include the identifier as well as the selected keywords, i.e., the user identifier and the user group identifier.

It is understood that one or more of the aforementioned embodiments of the invention may be combined as long as the combined embodiments are not mutually exclusive.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the ‘C’ programming language or similar programming languages. The computer readable program instructions may execute entirely on the user computer system's computer, partly on the user computer system's computer, as a stand-alone software package, partly on the user computer system's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user computer system's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions. 

What is claimed is:
 1. A computer-implemented method for managing search queries of a search service, wherein the method comprises: receiving, by one or more computer processors, a first search query from a client application, wherein the first search query compromises at least one boosting factor referring to at least one of a keywords of at least one of a content items of a search query type; executing, by one or more computer processors, the received first search query by the search service, wherein the search service comprises a search index with a set of content items and a search engine, wherein the set of content items comprises a set of one or more content items of a search query type, wherein each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword; in response to the executing of the first search query, providing, by one or more computer processors, a content item of the search query type comprising the at least one keyword referred to by the boosting factor as a first search result of the first search query by the search service; executing, by one or more computer processors, a search query with a user-defined search specification provided by the first search result as a second search query by the search service, in response to the executing of the second query, providing, by one or more computer processors, one or more content items as a second search result of the second search query by the search service; and sending, by one or more computer processors, the second search result as a search result of the received first search query to the client application.
 2. The computer-implemented method of claim 1, wherein the search service and a search query management component are provided by a content management system, wherein the query management component is configured for managing the receiving of the first search query from the client application and the sending of the second search result to the client application.
 3. The computer-implemented method of claim 1, wherein the content item of the search query type comprising the at least one keyword referred to by the boosting factor is provided in response to the executing of the first search query to the search query management component as part of a set of ranked content items of the search query type, wherein the search query type comprising the at least one keyword referred to by the boosting factor is the top ranked content item comprised by the set of ranked content items and selected by the search query management component for providing the second search query.
 4. The computer-implemented method of claim 3, wherein the ranking of the content items of the search query type is higher the more keywords referred to by the at least one boosting factor of the first search query the respective content item of the search query type comprises.
 5. The computer-implemented method of claim 1, wherein the first search query comprises as set of disjunctively connected sub-queries.
 6. The computer-implemented method of claim 5, wherein one of the disjunctively connected sub-queries comprises a search query identifier identifying the second search query.
 7. The computer-implemented method of claim 5, wherein one of the disjunctively connected sub-queries comprises as a boost query the boosting factor.
 8. The computer-implemented method of claim 7, wherein the boosting factor is assigned to a user identifier identifying a user of the client application.
 9. The computer-implemented method of claim 7, wherein the boosting factor is assigned to a user group identifier identifying user group comprising the user of the client application.
 10. The computer-implemented method of claim 1, wherein the method further comprises creating the content items of the search query type, wherein the creating comprises: determining, by one or more computer processors, one or more search queries comprised by a code of the client application; creating, by one or more computer processors, a content item of the search query type for each of the determined search queries, wherein the content item of the search query type comprises a second search query with the search query specification of the respective determined search query and a search query identifier identifying the respective second search query; storing, by one or more computer processors, the created content items of the search query type in the search index of the search service; updating, by one or more computer processors, the determined search queries for use as first search queries by the client application.
 11. The computer-implemented method of claim 10, wherein the updating comprises storing, by one or more computer processors, the updated search queries in the search application and replacing invocations of the determined search queries comprised by the code of the client application by invocations of the updated search query.
 12. The computer-implemented method of claim 10, wherein the content management system further provides an authoring service which enables creating and editing content items, wherein the authoring service is used by the search query management component for the creating of the content items of the search query type.
 13. The computer-implemented method of claim 10, wherein an overview content item comprising an overview over the determined search queries updated and the content items of the search query type created is provided in the search index, wherein the method further comprises updating, by one or more computer processors, the overview content item for each of the determined search queries updated and each of the content items of the search query type created.
 14. The computer-implemented method of claim 1, wherein the method further comprises implementing, by one or more computer processors, the query management component as a target for search queries received from the client application.
 15. The computer-implemented method of claim 1, wherein the method further comprises: receiving, by one or more computer processors, by the search query management component a first search query from the client application comprising a modification intention identifier identifying an intention for a user-defined modification; forwarding, by one or more computer processors, the received first search query with the modification intention identifier by the search query management component to the search service for executing; in response to the forwarding, receiving, by one or more computer processors, by the search query management component a set of one or more ranked content items of the search query type from the search service; selecting, by one or more computer processors, a top ranked content item of the search query type from the set of ranked content items of the search query type by the search query management component; in response to a detecting of the modification intention identifier of the received first search query by the search query management component, sending, by one or more computer processors, the selected top ranked content item of the search query type as a search result of the received first search query with the modification intention identifier to the client application for displaying on a user interface.
 16. The method computer-implemented of claim 1, wherein the search query management component is further configured for implementing user-defined search queries, wherein the implementing of a user-defined search query comprises: receiving, by one or more computer processors, by the search query management component a user-defined version of a content item of the search query type in the search index from the client application, wherein the user-defined version comprises a search query specification of the respective content item of the search query type in the search index with one or more user-defined modifications, a search query identifier identifying the respective search query of the respective content item of the search query type and depending on a user-defined scope for the modification the user identifier identifying the user of the client application or a user group identifier a user group comprising the user client application of the as a keyword, storing, by one or more computer processors, the user-defined version of the content item of the search query type in the search index.
 17. The computer-implemented method of claim 16, wherein the content management system further uses the authoring service for the implementing of user-defined search queries.
 18. A computer program product for managing search queries of a search service, the computer program product comprising: one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media, the program instructions comprising: program instructions to receive a first search query from a client application, wherein the first search query compromises at least one boosting factor referring to at least one of a keywords of at least one of a content items of the search query type; program instructions to execute the received first search query by the search service, wherein the search service comprises a search index with a set of content items and a search engine, wherein the set of content items comprises a set of one or more content items of a search query type, wherein each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword; in response to the executing of the first search query, program instructions to provide a content item of the search query type comprising the at least one keyword referred to by the boosting factor as a first search result of the first search query by the search service; program instructions to execute a search query with a user-defined search specification provided by the first search result as a second search query by the search service, in response to the executing of the second query, program instructions to provide one or more content items as a second search result of the second search query by the search service; and program instructions to send the second search result as a search result of the received first search query to the client application.
 19. The computer program product of claim 18, wherein the search service and a search query management component are provided by a content management system, wherein the query management component is configured for managing the receiving of the first search query from the client application and the sending of the second search result to the client application.
 20. A computer system for managing search queries of a search service, the computer system comprising: one or more computer processors; one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media for execution by at least one of the one or more computer processors, the program instructions comprising: program instructions to receive a first search query from a client application, wherein the first search query compromises at least one boosting factor referring to at least one of a keywords of at least one of a content items of the search query type; program instructions to execute the received first search query by the search service, wherein the search service comprises a search index with a set of content items and a search engine, wherein the set of content items comprises a set of one or more content items of a search query type, wherein each of the content items of the search query type comprises a user-defined search query specification of a search query for use by the search service and at least one keyword; in response to the executing of the first search query, program instructions to provide a content item of the search query type comprising the at least one keyword referred to by the boosting factor as a first search result of the first search query by the search service; program instructions to execute a search query with a user-defined search specification provided by the first search result as a second search query by the search service, in response to the executing of the second query, program instructions to provide one or more content items as a second search result of the second search query by the search service; and program instructions to send the second search result as a search result of the received first search query to the client application. 